Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 013 / update50.arc / UPDATE50.DOC < prev

Wrap

Text File | 1986-10-22 | 84.8 KB | 1,761 lines

UpDate v5.0 [UPDATE.COM compiled 22 October 1986] User's Manual ------------- TYPE this manual to your printer with PRINT.COM! ================================================ System Requirements: IBM PC/XT/AT or IBM-compatible computer One or more hard-disk drives and(or) One or more floppy drives [Floppy-Only Systems require High-Capacity Drives] ---- 80-column screen PC-DOS or MS-DOS v2.1+ 192K RAM Copyright Holder hereby grants permission to copy and distribute UpDate programs freely, on condition that no charge whatsoever is levied for, and no change is made in, UpDate programs. Parts of this software were created using the ZBasic(TM) Compiler. Portions of this Code are (C)Copyrighted, 1985 by Zedcor Inc. This software is provided FREELY on an "as is" basis, WITHOUT ANY WARRANTY, express or implied. IN PARTICULAR, the author disclaims all warranties or fitness for ANY purpose, and the user waives ALL claims against author for special, direct, indirect, or consequential DAMAGES arising out of or in connection with the use or performance of this software. READ THE DOCUMENTATION BEFORE USE! Please report bugs/criticisms/suggestions to Copyright Holder. Copyright (C) 1986 R. J. Holmgren 410 Central Park West New York, New York 10025-4855 Voice: (212)749-7882 Messages: PCSI (Dan Doman) BBS (212)529-0498 UpDate User's Manual UpDate Preliminary (MUST READ!). ----------- ========= N.B. 5.0 is an entirely New version of UpDate. Users of ANY earlier version of UpDate (before 5.0) MUST follow the "Quick Start" instructions, and then review the summary of "Major Changes to UpDate" below. Purpose. ======= UpDate economically maintains archival filesets, as "backup" insurance. It identifies and makes exact byte-for-byte COPYies of files newly-created or changed since the last time you executed the UpDate procedure. You may copy to/from one or more hard-disks, floppy drives, and/or RAM disks. An UpDate sub-system locates and copies files of OLDER date (e.g. ARChived and LiBRaried files) which have been NEWLY ADDED to your monitored directories. Configuration file PATHS.CNF pre-selects the range of directories and/or files to back-up (as well as specific filenames within this range to Skip and not back-up). PATHS.CNF enables UpDate to run without re-configuration every day, and copy the files you consider important. A screen editor simplifies installation. At runtime you copy, skip, or delete files. File-related information may also be sought, or DOS-level tasks (e.g. edit, list) performed. Dates and times may be altered to recapture files and repeat backup routines from any previous moment in time, to any backup destinations (floppy and/or hard-disk). For single hard-drives, UpDate offers a fast hard-disk alternative to the usual "swap-floppies" back-up routine: a "Parallel destination directories" option. UpDate is NOT SUITABLE for a floppy computer system equipped ONLY with low-capacity diskette drives! Note for NEW Users. ================== You will NOT be able to install UpDate successfully without reviewing the following documentation! UpDate is NOT "similar to" other programs. UpDate implements a large set of user-defined variables which control source and target drives, directories, and files. This documentation explains UpDate carefully. Proper one-time installation pays off in automatic daily execution. (Like a lot of software, UpDate's explanation is more complex than its operation, which is quite straightforward.) (page 2) UpDate User's Manual Quick Start Instructions for OLD Users: ====================================== Summary of File_Names/Changes: Delete UPDATE.BAT (UpDate no longer uses batch files). UPDATE.COM supercedes old UP.COM/EXE [delete UP.COM or UP.EXE]. LASTDATE.CNF must be deleted and replaced. PATHS.CNF must be re-Tested from UPDATE T, and old "Floppy-Only"[&F] or "Hard- Only"[&H] path specification suffixes must be altered to read "&1" or "&2". Instructions ------------ 1. TYPE and note the last backup date/time values and system parameters indicated in the 15 characters of your old LASTDATE.CNF file, coded: yymmddhhmmabdgh yy - Year of Last UpDate mm - Month dd - Day hh - Hour mm - Minute a - Old "Floppy" Drive Letter (New "Target 1" Drive) b - Old "Hard" Drive Letter (New "Target 2" Drive) d - Old "Hard Drive" Directory Designation (New "Dir Type Target 2") g - Selective/Universal Copy Mode default [M or S] h - Old CopyFile Link [Y or N] 2. DELETE these files in the old "UpDate module directory": DEL LASTDATE.CNF DEL UPDATE.BAT DEL UP.COM (or UP.EXE) DEL ZQ*.* (at least one ZQ* file should exist) 3. ARChive UPDATE50.ARC contains two files: UPDATE50.COM and UPDATE50.DOC (this file). REName UPDATE50.COM to a convenient filename, e.g. UPDATE.COM or U.COM (the documentation calls this file "UPDATE.COM"). 4. From DOS, command UPDATE T<cr> Edit your current PATHS.CNF file | Change any old "&F" Path spec suffixes to "&1" | Change any old "&H" Path spec suffixes to "&2" Test the file FIX ALL REPORTED ERRORS! 5. From DOS, command UPDATE<cr> A new LASTDATE.CNF will automatically be prepared. System parameters will be solicited first, then the "last" backup date and time. Use some of the old values noted from instruction 1, above (coded a-h to correspond to NEW parameter labels). (page 3) UpDate User's Manual Major Changes to UpDate. ======================= UpDate has been radically revised, although the basic purpose remains the same (see "Purpose", above). UpDate now functions like a flexible Sweep- type program. New features: ------------ Two "Target drives" are supported. UpDate treats Target 1 and Target 2 destinations equally (formerly, distinct "Floppy" or "Hard" targets had different persona and capabilities). The ONLY unique difference between Target 1 and Target 2 is that Parallel directory organization (the option to UpDate specified directories on a single drive to "Parallel" directories located on the same drive) is supported on Target 2 only. UpDate writes a new LASTDATE.CNF [and optional Old CopyFile archive ARCH- UPD.CNF] file to disk ONLY after processing is completed normally. An "Abort" (runtime command "A" in Selective Copy Mode) retains the current files/defaults (this simplifies repeat runs and error recovery) Full file information (date, size, etc) is reported to the console at each copy step New "Selective Copy Mode" Features: ---------------------------------- Copy Nonstop to the end of a directory (runtime command "N"). Nonstop processing halts automatically if CopyFile is missing on Target drive. User can also halt Nonstop processing at any time with Function Key <F1>. Continuous "If_Exist" check for Filename on Target disk (enables repeated floppy swaps until the correct target diskette is located). This check is OPTIONAL; it is switched ON, for either or both Targets, by means of LASTDATE.CNF parameters e) and f). When ON, If_Exist target checks occur automatically with runtime command "C"opy. Override the "If_Exist" target check for any file, and Copy to target (runtime command "O") Delete Source AND Target 1 or 2 files [both optional] (runtime command "-") Abort at any stage of processing (runtime command "A") View the List of CopyFiles (runtime command "V") Select file EXTensions (e.g. BAK) to delete from all specified directories on each UpDate run (parameter "i" of LASTDATE.CNF). Ten "delete extensions" are supported. N.B.: BAK and TMP extensions are NOT automatically deleted, as in earlier versions of UpDate; EXTensions must be specifically designated by the user as "Delete EXTensions". However, you may still use the old "inhibit deletion" trick -- specify wildcards or filenames in PATHS.CNF -- to prevent deletion of any EXTensions in particular (but NOT all) directories. === Shell to DOS (runtime command "D"). Be sure to command EXIT from DOS (i.e. return to UpDate) ONLY from the directory in which UPDATE.COM is located! Reverse the direction of copy processing [repeat operations] (runtime command "R") (page 4) UpDate User's Manual Run DOS-level scripts (runtime command "S"; store scripts in parameter "j" of LASTDATE.CNF). Edit a file, check free space, etc. Nine scripts are supported; you can List them at runtime if you forget the number of the Script to execute. Scripts are used during copy processing (to perform some oft-repeated DOS function, or load a file, e.g. a text editor); on termination, UpDate returns to the same point in processing. OPTIONAL command line parameters may be invoked at runtime by entering the NUMBER of the Script at the Script prompt, followed by a space and the parameter(s). Example scripts: FREE A: (check available space on the A: drive diskette) FREE (enter drive parameters at runtime, e.g. if "FREE" is script #1, type "1 B:" to execute DOS command "FREE B:") EDLIN (enter [\path\]filename to edit at runtime) COPY ARCH-UPD.CNF OLDARCH.CNF (make an extra copy of the Old CopyFile archive, to be able to re-run UpDate with the same results for Old files) Old functions retained: ---------------------- Optionally: UpDate ALL files newly ADDED to or CHANGED in specified directories REGARDLESS OF FILE-CREATION DATE (this option, activated by entering "Y" in LASTDATE.CNF parameter "h", is integrated with standard UpDate; files flagged with this option are marked "OLD"). Thus, files acquired by modem or transferred from a diskette, and located in any directory specified in PATHS.CNF, are automatically UpDated. DOS file SORT.EXE must be present in the same directory as UPDATE.COM (Sorry! SORTF by Buerg is not supported - you MUST use the IBM/Microsoft utility, which is slower but universally available.) [Formerly, this "Copy Old Files" function was called "UPDATE N".] LIST or TYPE files to console (runtime command "L"). Vern Buerg's LIST60H.COM is currently the best List utility; rename it LIST.COM and locate it in the SAME directory as UPDATE.COM Old function ELIMINATED: ----------------------- SEPARATE operation of UPDATE N (Linked operation still supported) -------------------------------- Old documentation ERROR: ----------------------- Write PATHS.CNF only with UPDATE T, not with a word processor! Note Concerning "Universal Copy Mode": ------------------------------------- The usefulness of "Universal" Mode is reduced in v5.0 due to the new flexibility of "Selective Copy Mode", which should be the Default Copy Mode for most applications. (page 5) UpDate User's Manual The main feature of "Universal" Mode is high-speed automatic (hands-off, one-keystroke) "Nonstop" processing of copyfiles. In "Universal" Mode: Discretionary "Copy, Override, Abort, DOS, List, Reverse, Script, View, and - Delete" commands DO NOT FUNCTION! There is NO "If_Exist" CHECK for copy_filenames on target drives/disks. UpDate DOES NOT PAUSE at the end of directories EXCEPT if a Target drive is lettered A or B, in which case a FLOPPY TARGET IS ASSUMED (for Target drives A or B, UpDate stops at directory-end to permit a diskette swap). Pressing any key other than "C" will Skip (e.g. if you can't find the proper diskette). UpDate WILL PAUSE if the Target disk is full, to enable a swap. UpDate MAY be halted at any stage with function key <F1>; the effect is that UpDate is toggled into "Selective" Copy Mode ("Universal" mode is resumed with the Nonstop command). Thus, in practice, most users will probably want to restrict "Universal" copy mode to file copying between two hard disks, or between RAM disks and hard disks, with ample free space on the target. Runtime "Selective/Universal" copy modes are toggled with Main Menu switch "4" before copy processing begins; the default Copy Mode is fixed in LASTDATE.CNF parameter "g"). Memory and Disk-Space. ===================== UpDate is not memory-resident. During operation UpDate will utilize (briefly, then relinquish) a variable amount of disk space in the UPDATE.COM directory (typically 8K to 50K). Dates and Times. =============== UpDate assumes that your computer knows the CORRECT current date and time. If your computer does not automatically keep track of the current date and time, you MUST enter these two figures with reasonable accuracy when you power-up -- otherwise, UpDate WILL NOT WORK (place DATE and TIME statements in the root directory's AUTOEXEC.BAT file). If you mis-calibrate DOS's intrinsic DATE or TIME functions, or deliberately advance UpDate's record of the "last" backup date and time, UpDate may omit backups. UpDate's internal "LASTDATE clock" [not the DOS clock] comprehends the period 1 January 1977-31 December 2076. Do NOT attempt to set this UpDate clock to a "future" date (i.e. a date subsequent to the "current" date recognized by DOS); UpDate will reject it. U.S.A. Time/Date Formats: UpDate REQUIRES that DOS directory date/time formats, e.g. "11-19-86 11:02a", conform to those of the U.S.A. (page 6) UpDate User's Manual (the default setting of most IBM microcomputers; otherwise place the statement COUNTRY=001 in your CONFIG.SYS file). First-Time Setup/Configuration of UpDate. ======================================== Console prompts explain most procedures. In addition to system file UPDATE.COM, UpDate will configure (before its first run, with data which it interactively obtains from the user) the "path specification file" PATHS.CNF. PATHS.CNF informs UpDate which source drives, directories, sub-directories, or filenames you have elected to back-up regularly. Usually these are the active disks, directories, and/or files with which you work daily. For its own internal use, UpDate will create (on the first run, with user input) and thereafter maintain a set-up parameter and date/time record called LASTDATE.CNF. File LASTDATE.CNF records the target drives, the default values of program parameters and switches, and the date & time of the "last" previous run.1 INSTALL UpDate system file UPDATE.COM in any hard-disk directory or subdirectory, on any drive. Buffers: A reasonable number of disk buffers (determined by a "BUFFERS=number" statement in boot file CONFIG.SYS) will dramatically accelerate UpDate operation, and may affect many or all of your other programs. Typical statements are BUFFERS=15 for a ten megabyte hard-drive, or BUFFERS=30 for a twenty meg drive. You can roughly determine the optimum number of buffers for your computer by stopwatch-timing the operation of DOS utility CHKDSK with different BUFFER=n statements. Too many or too few buffers both retard computing speed, so fine-tune. UpDate Path Specification File PATHS.CNF ======================================== Before using UpDate you MUST describe, in PATHS.CNF, as much of the directory structure of your hard (or high-capacity floppy) disk(s) as you wish to UpDate on a regular basis. Usually, you create PATHS.CNF before your first use of UpDate, and then forget about it. -------- 1 The following filenames are reserved for the exclusive use of UpDate; do not locate any other files with these names in the UpDate directory: UPDATE.COM; PATHS.CNF; LASTDATE.CNF; ARCH-UPD.CNF [UpDate Old CopyFiles option only]; ZQ?.* (page 7) UpDate User's Manual UpDate's built-in editor (UPDATE T) collects -- then organizes, re- writes, and tests -- data which you provide to PATHS.CNF. You supply PATHS.CNF with as many as 255 path or path+filename specifications, or as few as 1 (an advantage of UpDate is that the range of files backed-up regularly can be very broad, or precise and narrow). The broadest specifiable PATHS.CNF instruction is to copy a whole directory; the narrowest instruction is to copy one file. You may NOT specify an entire drive, except by mentioning all (sub)directories on that drive. You may backup source files on SEVERAL source drives. You can specify particular filenames to backup with UpDate, and/or use the DOS universal wildcards "?" and "*". You may type path specifications in UPPER or lower case (UpDate path test utility UPDATE T translates all characters to UPPER case). Every path specification begins with a root drive designation and a foreslash (e.g. C:\), which indicates that paths to the source directory or filename(s) are described from the source's root directory (regardless of whether UPDATE.COM itself is located in the root or in another directory, on the specified drive or on another drive). Each specified path can be described in 73 characters WITH filenames, or 60 characters WITHOUT filenames (no blank spaces permitted, except in below-described "Skip", "Target 1-only", and "Target 2-only" filename specifications).2 You must specify ALL directories which you wish to UpDate, including the current UPDATE.COM directory and/or the root directory. You may specify exceptional `Skip' filenames, within a broader back-up category, which should NOT be backed-up. Some programs incessantly re-write inconsequential auxiliary files or indices, which need never be copied; it is annoying to confront them each time you UpDate. If -- and ONLY if -- you UpDate to BOTH Target drives, UpDate can restrict the backup destination of SOME source directories to just Target 1 or Target 2, while ALL OTHER directories/files continue to be sent to BOTH Target destinations. This option is RARELY needed (e.g., if hard disk space is -------- 2 Avoid long strings of intricate, literal sub-directory names like \ADMINISTRATION\INVENTORY\ACCOUNTING\RECEIVABLES\DEADBEATS, which are designed for novices but excruciating for everyone: use instead brief mnemonics like \ADMIN\INV\ACC\AR\BUMS, or better yet \AD\I\A\R\B. (page 8) UpDate User's Manual limited). See section entitled "Target 1-Only and Target 2-Only Path Specs", end of this manual. Configure path specifications in PATHS.CNF: Procedure. ------------------------------------------------------ In the UPDATE.COM directory, from DOS, type UPDATE T <carriage return> (the "Enter" key, hereinafter called <cr>). Note the space between UPDATE and T. If no PATHS.CNF file currently exists in the UpDate directory, UpDate loads an editor that prepares a PATHS.CNF file for you. Each path (or narrower path + filename) specification occupies a separate line in the PATHS.CNF file, and has the same format. Enter first the single-letter designation of the drive on which the SOURCE directories or files to be backed-up are located (e.g. C). UpDate immediately displays this driveletter plus the syntactical characters :\ and then invites you to complete the full path specification. Enter a lone <cr> if you wish to specify the ROOT DIRECTORY ONLY (e.g. C:\); otherwise write the rest of the path specification (e.g. C:\TEXTS), then <cr>. If you make a mistake in one specification, you could write it correctly in the next specification, and then delete (or else modify) the bad line when you Edit your file after entering all New specs. The "Enter New path spec" procedure loops until you <cr> at the first prompt, to Quit entering New lines. Then Edit (if necessary) the file (see below). To Skip particular filenames (assumed to be included within more encompassing path specifications), write a normal path spec (one of 255 maximum) indicating the complete drive:\path\filename[.extension] -- NO wildcards are permitted in Skip specs! Then add a single blank space, plus an ampersand and letter S ( &S). UpDate requires a separate "Skip filename specification" for EACH individual file to be skipped. A sample PATHS.CNF file (with gloss): C:\ (copy all files in the root directory) C:\A (copy all files in directory \A, except ...) C:\A\CONTROL &S (a "Skip filename specification" [with appendage &S] for file CONTROL [no .EXTension] in directory \A) C:\B\*.DAT (copy all \B directory files with extension .DAT) C:\NAOMI\ART\INDIAN (copy all files in sub-directory \INDIAN with path from the root directory described as \NAOMI\ART\INDIAN) D:\VOL\CHAPTER?.TXT (copy chapter numbers 1-9 using ? wildcard) D:\WEIGHTY.TOM (copy only file WEIGHTY.TOM on the D: drive root directory) (page 9) UpDate User's Manual Observe that, in PATHS.CNF, you give no direct instructions to the system; you do not indicate any operations (e.g. COPY) to execute, nor do you state the destination drive or directory for those operations, because UpDate performs all these functions for you. You simply describe PATHS from the ROOT to the DIRECTORIES and/or FILES which serve as sources for UpDate. (The location of UPDATE.COM itself is irrelevant.) First-time users: Specify one directory only for starters, to get a feel for the program. In practice, users who require very tightly-defined PATHS.CNF files have two choices: either to specify only those individual path + filenames which will be monitored, or else to specify broader directory or filename categories and then use "Skip filename specifications" to exclude unwanted files. IN MOST CASES, a liberal use of "Skip filename specifications" is preferable, because you cannot anticipate the names of files which you may create in future, but you will undoubtedly wish UpDate to find and copy (or at least signal the fresh presence of) those new files. Whereas, it will be clear at outset that certain existing files are of no importance and can be skipped; thenceforth, new "Skip specs" will be added one by one, as particular files become pests. The presence in PATHS.CNF of 40 or 80 "Skip filename specifications" has NO discernible effect on UpDate processing speed, but many narrow copyfile specifications will slightly prolong file-scanning and -sorting at the outset of UpDate. Nevertheless, if you have a byzantine directory organization and wish simply to monitor a few files in each directory, then specify filenames to copy -- the speed differential is slight. Edit a pre-existing PATHS.CNF file. ---------------------------------- Type UPDATE T from DOS. The screen offers four options: select the first, E for Edit <cr>, and look at your existing list of specifications. To EDIT (change) a line in PATHS.CNF, enter the line number <cr>, then alter the contents of the line. You can edit (using insert, backspace, delete, and cursor keys) just like a word processor. To DELETE a line, enter the line number <cr>, then hit a Minus sign - (no <cr>!) as your FIRST key struck. If you enter a minus sign after the FIRST key is typed, it becomes a true character in the path spec. To ADD a line, type "N"<cr> for New, and append a new line to the file. LIST and examine the file's contents by pages (type "L"<cr>) as often as necessary (to learn which line numbers you wish to Edit). (page 10) UpDate User's Manual Each time you add/modify/delete a line in PATHS.CNF, the entire file is re-displayed in its new form, for perusal. You may edit, add, and/or delete as many lines as you choose, in any order. UpDate alphabetizes the specifications whenever they are re-displayed, and thus line-numbering may change. Some simple errors in specifications are corrected at this stage; other subtler problems are examined ONLY when you Test the file after entering all your Path specs. Type "T"<cr> to quit editing. UpDate now automatically Tests your PATHS.CNF file for validity. Type "Q"<cr> to Quit to DOS (no Test) ONLY if you intend to re-enter and Test the file later. Test validity of PATHS.CNF. -------------------------- You MUST REPEAT the error-trapping UPDATE T "T"est option until you achieve an error-free PATHS.CNF file: UpDate will crash (!) without a valid PATHS.CNF, and it will run very erratically, or not at all, if the Test has not re-organized a new or revised PATHS.CNF prior to use. Test an existing PATHS.CNF file by typing UPDATE T <cr> from DOS, and select the second of four menu options, Test, by entering "T" <cr>. You can also Test after Editing, as noted above. Error-checking is performed by both UpDate and DOS. If you have specified an invalid/nonexistent path or filename, or use an improper syntax, UPDATE T halts and points to the problem. If there is a DOS error (e.g. a forbidden character such as a comma in a spec), DOS responds "Bad command or file name". REPAIR ALL ERRORS by re-loading the UPDATE T editor. N.B.: If you are UNFAMILIAR with DOS, test your PATHS.CNF file more than once! Really preposterous errors may only be eliminated after several passes. PATHS.CNF is error-free ONLY if UpDate signals "PATHS ARE OK!" on completion of the Test AND no "Bad command or file name" error-messages appear. === N.B.: The UPDATE T test does NOT THOROUGHLY EVALUATE "Skip filename specifications" [ &S] for validity (the proof resides in the pudding only). Note: Two special situations cause UPDATE T to flag a path as "Bad": 1) If, at the end of a path, you specify a filename which has NO EXTENSION, e.g. C:\ART\OBJECTS, UpDate can't tell whether OBJECTS is a sub-directory of directory ART, or a filename with no extension called (page 11) UpDate User's Manual OBJECTS which exists in directory ART -- by convention, UpDate defaults to the former assumption (that OBJECTS is a sub-directory), and UPDATE T crashes if OBJECTS is actually a filename. Solution: To distinguish the two, write filenames with no extension in the form C:\ART\OBJECTS.*, adding a ".*" wildcard extension. But do NOT (!) add wildcards or superfluous extensions to "Skip filename specifications" [ &S]; enter each individual Skip spec in PATHS.CNF precisely as it appears in the DOS directory, with or without an extension, and then append " &S" to the line. 2) Directories which contain NO FILES at all, or which do not presently contain a specified filename, are always flagged "bad directories" by the UPDATE T test utility, even if they are properly described in PATHS.CNF. Moreover, UPDATE T halts and will not test the remainder of PATHS.CNF. Solution: Copy one file into every EMPTY directory, before testing paths; or place in the directory one real filename of the categorical type (e.g. *.DOC) specified, as a dummy that fulfills the test's need to find such a file present (e.g. re-name an existing file temporarily). Run UpDate. ========== To start UpDate: [Run UpDate ONLY from the directory in which UPDATE.COM is located.] Type UPDATE <cr> at the DOS system prompt. After a brief interval, during which your diskfiles are scanned and listed off-screen, the UpDate Main Menu (reproduced below) appears. Date and Parameter File LASTDATE.CNF. ==================================== If you are running UpDate for the first time, UpDate poses (and then records semi-permanently in file LASTDATE.CNF) ten set-up questions: a) Target 1 driveletter b) Target 2 driveletter Directory organization [M/R] on c) Target 1, Directory organization [M/P/R] on d) Target 2 = Check for existence of target_file [Y/N] on e) Target 1 f) Target 2 (page 12) UpDate User's Manual g) Level of copy/skip control [S/U] to be exercised over UpDate h) Use [Y/N] UpDate's "Copy Old Files" option (which keeps track of older-date files) i) EXTensions to delete on every run in every directory [max 10] j) Scripts to execute from DOS during processing [max 9]. The program then solicits a Date and Time that serve as a terminus ad quem for the UpDate processor: an estimate of when you "last" UpDated your files. Like PATHS.CNF, LASTDATE.CNF set-up is usually a one-time affair unless you change your system or elect to experiment with different configurations. You can optionally establish a new "last" Date and Time (and/or change the set-up parameters) ANYTIME you run UpDate, from within the program itself. Detailed explanation of the ten LASTDATE.CNF set-up questions (a thru j): ------------------------------------------------------------------------ a) Indicate the letter of the Target 1 disk drive (the first DESTINATION drive for copies). Enter this as a single letter, e.g. A, B, or any other drive_letter through Z. b) Indicate the letter of a second "Target 2" DESTINATION drive, if any. Designate the Target 2 destination with a single letter, e.g. D, E, or any other drive_letter A through Z. c) and d) Define the hard-disk DIRECTORY ORGANIZATION which UpDate will observe during operation, as explained in the discussions of "Copying between Two Drives" and "Parallel hard-disk back-up directories", q.v. section below entitled "Drive and Directory Organization". In brief, parameters c) and d) note whether UpDate shall collect back-ups in: M = "Mirror-image directories" which bear the same directory names as their sources, on a different backup drive; or R = One catch-all Root directory on a different hard drive. For Target 2 ONLY an additional option exists, to use: ------------- P = "Parallel backup directories" which bear slightly different directory names than their sources, and are located on the SAME drive as the source files. First-time users: Enter Root directories only ("R"<cr>). You may wish to change this entry (easily done) after you learn more about UpDate's options for drives/directories/sources/targets. (page 13) UpDate User's Manual e) and f) Perform a Check for the existence of the source filename on Target 1 (e) or 2 (f). Respond "Y"es or "N"o for each target. This is useful mainly with FLOPPY targets; it ensures that you've selected the correct diskette (thus you won't make two copies of the same file on different disks). g) Use "Universal" or "Selective" Copy Mode, explained in the following section entitled "Universal or Selective Copy Modes". First-time users should enter "S" for "Selective" mode (always adjustable at runtime); in "Selective" mode, you can skip all copying operations if your initial set-up is faulty. h) Search, on EVERY UpDate run, for all files with OLD creation dates which have been newly-added to the monitored PATHS.CNF directories, as well as for newly-created or -changed files. To search for BOTH, specify "Y"es; for newly-dated files only (standard UpDate), specify "N"o. This "Old Files" option takes more time, but it covers you completely, and backs up EVERYTHING newly WRITTEN in the specified directories. DOS file SORT.EXE must be present in the same directory as UPDATE.COM with this option. See section entitled "Locating and UpDating Newly- Added Files Bearing Old Dates", at end. First-timers: Enter `N'o. i) Specify file .EXTensions (1-3 letters) to DELETE on every run, in every directory. Ten "Delete Extensions" are allowed, e.g. BAK, TMP, TST, etc [give your fun files .TMP extensions, then get rid of them]. This is a cleanup and conservation measure. Deletion of files with these extensions occurs at the very BEGINNING of UpDate processing; there is NO opportunity to Abort or save such files once they are designated in LASTDATE.CNF and processing begins. N.B. Extensions designated with this parameter are deleted ONLY if an ENTIRE directory is being UpDated. If PATHS.CNF specifies particular FILENAMES or EXTENSIONS, including any combination of the WILDCARDS * or ? (e.g. "all files" designation "*.*", the functional equivalent of specifying a path without filenames), then no files with these .EXTensions are deleted. Example PATHS.CNF spec: D:\BOOK\*.* (copy all files in D: drive directory \BOOK, using *.* wildcards to inhibit automatic deletion of files with "Delete extensions") j) Specify DOS-level "Scripts" which can be executed during processing. Nine scripts are supported. Scripts are used during copy processing to perform some oft-repeated DOS function, or to load any file (e.g. a text editor); on termination, UpDate returns to the same point in processing. OPTIONAL command line parameters may be invoked at runtime by entering the Number (1-9) of the script at the script prompt, followed by a SPACE and the desired parameter(s). For sample scripts, see the "Major Changes to Update" information, above. (page 14) UpDate User's Manual The two LASTDATE.CNF Date/Time questions: UpDate's internal "clock" sets the Date and Time of the "last" back-up routine. Console prompts illustrate the correct form for Date and Time statements.3 On a first-time run, set the date back a few days, to copy numerous files and learn how UpDate works. LASTDATE.CNF need never be set manually again. In future, UpDate will automatically keep track of the last backup time, and continuously copy new files as necessary. But ANYTIME you wish to repeat the backup of, for example, yesterday's or last week's files, simply change the date (option 5 on the Main Menu) as UpDate begins, and enter a date which PRECEDES the time you created the files that are to be UpDated again (e.g. yesterday morning at 0000 hours [Midnight], to be sure that you catch all of yesterday's transactions). Altering the "last" date has no lingering effect upon UpDate, because UpDate will backup all changes (in the directories specified in PATHS.CNF) from e.g. yesterday morning until the present moment, and it will then make an internal note of the current correct Date and Time. -------- 3 For keystroke economy and intuitive order-of-importance logic, UpDate uses European date and time formats: DDMMYY (day month year) and HHMM (hour minute), e.g. 011286 (1 December 1986) and 1400 (2 PM). (page 15) UpDate User's Manual The LASTDATE.CNF Change Menu usually opens like this: * * * Last UpDate on 120586 at 0513 hours = Monday 12 May 1986 at 5:13 AM (Now: 130586 at 1340 = Tuesday 13 May 1986 at 1:40 PM) ============================================================================== REPLACE DATE/TIME RECORD Create a replacement LASTDATE.CNF file for UpDate. At the next (`Last backup date') prompt, Type: A<cr> to Abort changes & restore existing LASTDATE.CNF defaults; P<cr> to alter UpDate system Parameters; or ------------------------------------------------------------------------------ Last backup Date in form DDMMYY<cr>, e.g. 090586 = 9 May 1986 Enter the Last backup date: ------ . . . Enter the Last backup time: ------ * * * If in hindsight you decide that you don't really wish to change the "last" Date/Time, you can Abort to an existing LASTDATE.CNF record of these values by typing A <cr> at the "Last backup date" prompt. If you wish to ALTER THE SYSTEM'S SET-UP PARAMETERS, select main menu option 5 (no <cr>) after UpDate loads, then type P <cr> at the "Last backup date" prompt. After changing (or reviewing) parameters, type Y to accept the changes, or strike any other key and Abort to your existing LASTDATE.CNF file with "A"<cr> when the "Last backup date" prompt reappears again; no new LASTDATE.CNF file will be logged on disk. Never erase file LASTDATE.CNF! (page 16) UpDate User's Manual Run UpDate (continued). ====================== The UpDate Main Menu looks something like this: * * * Last UpDate on 220586 at 0638 hours = Thursday 22 May 1986 at 6:38 AM (Now: 220586 at 0651 = Thursday 22 May 1986 at 6:51 AM) ============================================================================== Selective Copy Mode Copy To: Options: ======= ======= 1 Hard Disk --, 4 Switch to Universal Copy Mode |=>3 BOTH 5 Change Last Date/Time, or Parameters 2 Floppy Disks --' 6 Abort to DOS * * * Main Menu Selections 1-3: Execute and Copy. ------------------------------------------ Strike 1, 2, or 3 (no <cr>) to execute UpDate. If you designate one Target drive only, UpDate offers only one valid "Copy To:" drive destination. Main Menu Option 4: Universal or Selective Copy Modes. ----------------------------------------------------- UpDate offers the option of "Universal" or "Selective" copying: at the main menu, type 4 to toggle between Universal and Selective copy modes. Toggling affects the current run only; the default copy mode is determined by set-up parameter g) in LASTDATE.CNF. "Universal" means that every new or changed file is copied to Target drive(s). Setting the LASTDATE.CNF default to "Universal" copy mode is the fastest (hands-off) method of backing up all files. HOWEVER, in MOST CIRCUMSTANCES you will want to use "Selective" copy mode, due to its enhanced flexibility. (See some considerations in the "Note Concerning Universal Copy Mode," above.) (page 17) UpDate User's Manual In "Selective" copy mode, UpDate pauses to enable a deliberate decision about each file, with a group of options. The screen prompt might look like this: * * * Copy C:\P\LASTDATE.CNF 128 10-12-86 4:33a to Target 1> A:\P Copy Nonstop to Directory End -Delete Abort DOS List Reverse Script View_CopyFiles [other key Skips]: * * * The program always reports: source drive\path\filename; filesize in bytes; file creation date and creation time; and Target number> drive\path. Universal Mode Operation. ======================== See the "Major Changes to Update", above, for a description of "Universal Copy Mode". Selective Mode Operation. ======================== A menu of processing options appears: Strike "C" to Copy file to target. If LASTDATE.CNF parameter e) or f) is set to "Y" for Target drive 1 and/or 2, a check for the existence of the filename is performed on the Target disk; if filename does not exist, a warning message is displayed. You may then hit "O"verride, and copy to the target regardless of the absence of the filename, or you may swap diskettes and strike "C"opy again, to check again. This check can be pursued indefinitely, until the proper diskette is located, in which case copying occurs immediately (causing the screen message "1 File copied"). If LASTDATE.CNF parameter e) or f) is set to "N" for a Target drive, NO check for the existence of the filename is performed; the copy is simply made. If free space on the Target disk is inadequate, UpDate DELETES THE TARGET FILE and Halts to permit the diskette to be swapped. (page 18) UpDate User's Manual Strike "N" to Copy NONSTOP (all targets) to end of the current directory. Nonstop processing will halt and revert to ordinary Selective processing whenever: 1) the end of the directory is reached; 2) a check for existence of a filename on a target fails; or 3) Nonstop processing is manually halted with function key <F1>. Resume Nonstop processing by commanding "N"onstop again. Strike "-" to Delete Source (and, optionally, Target) files. To Delete a file, you must hit a minus sign (-) key TWICE, as a precaution against fatal user-error (ABORT DELETION by hitting ANY OTHER KEY than a minus sign at the second delete prompt). "Delete" erases the Source file first. If, and only if, you delete the Source, you may also delete Target files of the same name on Target directories or disks. If there are two Targets, you may delete the file from either or both destinations; e.g., although you abort deletion on Target 1, you may still delete Target 2. N.B.: No genuine check is performed for the existence of the filename on the Target(s). The logic of this command is: "if exist filename then delete filename"; but if filename does not actually exist, no action occurs. In EITHER case, the program returns "OK". Deletions are final, and unrecoverable with DOS. Strike "A" to Abort to DOS [quit UpDate]. Consequences: No new LASTDATE.CNF file is written to disk, unless you have previously changed [and written] LASTDATE with Main Menu option 5. The next UpDate run will reflect the same "Last backup date" as the present run. This is an easy way to repeat UpDate with identical results if you have made mistakes. The current ARCH-UPD.CNF is also preserved (New feature of v5.0). Strike "D" to Shell to DOS. IMPORTANT!! Return ("EXIT") from DOS to UpDate ONLY from the UPDATE.COM directory! UpDate calls several files located in this directory; if it does not find them, the consequences are UNPREDICTABLE! Obviously, you are "on your own" when you go to DOS. Avoid actions with consequences for UpDate; these include deleting a file on the UpDate "List of CopyFiles", or altering or UTILIZING any filename "ZQ*.*". Strike "L" to List or Type the current copyfile to the console. If a LIST- or BROWSE-type utility is placed in the UPDATE.COM directory, any file flagged by UpDate can be displayed on-screen utilizing the full functionality of this LISTer. However, if no filename LIST.COM or LIST.EXE is located in the UpDate directory, UpDate uses the DOS internal command TYPE to display files. (page 19) UpDate User's Manual Note that you must RENAME the BROWSE.EXE, PIBLIST.EXE, LIST60H.COM, or similar utility which you locate in the UpDate directory to filename LIST.EXE or LIST.COM. UpDate assumes that your lister accepts drive and path parameters (check whether it can read a file in another directory or drive, before installation in the UpDate directory). A splendid public domain shareware program available on most BBS is LIST.COM by Vern Buerg. If you use DOS command TYPE, pause TYPEing with <Ctrl+NumLock> (resume TYPEing with any key). Abort TYPEing and return to UpDate with <Ctrl+Break>. Backscrollers such as WAITASEC.COM (a PC Magazine PD program, 26 Nov 85) provide some flexibility. Strike "R" to Reverse the direction of copy processing. Move backwards in the "List of CopyFiles", i.e. repeat one or more copy opportunities. Strike "S" to run DOS-level Scripts. Scripts are stored in parameter "j" of LASTDATE.CNF; they can be revised/added/deleted either with UPDATE T's "C"hange LASTDATE.CNF command, or at option 5 of the Main (runtime) Menu. Nine scripts are supported; you can List them if you forget the number of the Script to execute. Scripts shell to DOS and permit you to load a word processor, check free space, or perform ANY other DOS function, during copy processing. When the script terminates, UpDate returns to the same processing step. Generally, Scripts are functions which are repeated so often that it is more convenient to set them up within UpDate, and run them automatically, than to use UpDate's "D"OS shell command and enter them from scratch. Command line parameters may OPTIONALLY be invoked at runtime by entering the number of the script at the script prompt, followed by a space and the parameter(s). See the "Major Changes to Update", above, for sample Scripts. Strike "V" to View the "List of CopyFiles". Find out where you are -- what you've already done, and what remains to be done -- in the sequence of UpDate processing. A LIST utility, or DOS internal command TYPE, is used to display UpDate's "List of CopyFiles" (q.v. the "L"ist runtime command, above). Strike ANY OTHER KEY to Skip the current file-copy opportunity. Proceed to the NEXT file awaiting copying (or move from Target 1 to Target 2 for the SAME file), to be offered the same menu of processing options again. (page 20) UpDate User's Manual Main Menu Option 5: Change `Last' Date/Time, or System Parameters ----------------------------------------------------------------- See above, discussion of LASTDATE.CNF set-up and Date/Time questions. Main Menu Option 6: Abort to DOS -------------------------------- Option 6 quits to DOS with the same consequences as the "A"bort runtime command, discussed above in Main Menu Option 4. Run UpDate (continued). ========== When you start UpDate from the Main Menu, a list of files that were altered or added since your last UpDate passes by the screen twice, the first time for information only (file sizes, etc), the second time as copy operations proceed. Changed files which will be omitted due to PATHS.CNF "Skip filename specifications" are also listed on the first pass, with the label [SKIP] appended -- as an advisory only. UpDate processing begins when UpDate searches through the directories specified in PATHS.CNF and finds at least one new or changed file. If UpDate system file LASTDATE.CNF is encompassed within a PATHS.CNF source specification, LASTDATE.CNF will appear in the first advisory screen listing of files; but if no OTHER New or Changed files are found, UpDate ENDS with the message "No Files Were Changed Since Last UpDate", and the current LASTDATE.CNF remains the file of record. If LASTDATE.CNF parameter e) or f) instructs UpDate to perform a check for the existence of copy filename on a Target, UpDate inquires for the file on the designated Target drive/disk. If the file is not present, a "WARNING" bell sounds with a message. If the target is a floppy, you MAY have inserted the wrong diskette; but if the file is brand-new, no backup copy will exist, so hit "O"verride to bypass repeated target checks and make the copy. When insufficient space remains on the target drive, a bell rings with the message "DISK FULL!". If the Target is a floppy, you can swap diskettes and try again; the error message will recur until you find a diskette with adequate free space. But if the target is a hard-disk, you'll need to Skip and start housecleaning. (page 21) UpDate User's Manual Drive and Directory Organization. ================================ Copying between Two Drives. -------------------------- Preliminary: UpDate copies source files from one drive, to destination directories on another drive. For an explanation of "Mirror-image" and "Root drive-only" copying [LASTDATE.CNF parameters c) and d)], SEE 1) BELOW. For "Logical" drives, i.e. SINGLE drives which have been partitioned into several separate "logical" drive designations (e.g. C:, D:,...Z:), SEE 2) BELOW. For RAM drives, or virtual memory "drives" which mimic logical drives and possess separate drive_letter designations, SEE 3) BELOW. UpDate offers a unique method of backing-up to the SAME hard-drive if you just have ONE. This technique, called "Parallel backup directories", has distinct advantages and disadvantages. Consider it only if you have a SINGLE hard drive: SEE 4) BELOW. With restrictions, FLOPPY-ONLY systems may also use UpDate: SEE 5). 1) Copying between Two Drives. ------------------------------ The directory(ies) to which files are written on Target drive(s) are selected in LASTDATE.CNF directory organization parameters c) and d). Usually, there are two choices: "M" for `Mirror-image copy directories'; or "R" to collect all copies in the Root directory regardless of source directory. (`Parallel copy directories', "P", are another option, explained in paragraph 4, below.) M = Mirror-image. A "Mirror-image" of the Source drive means that, for (sub)directories specified in PATHS.CNF, the "tree" of the Source drive is replicated precisely on the Target drive (e.g. if C:\ART\LETTERS is a subdirectory of Source drive C:, UpDate requires a D:\ART\LETTERS subdirectory on Target drive D:). Make "Mirror-image" copying your default by responding "M" in parameters c) and/or d). Note that you MUST create directories on your Target drive(s) which are identical to those on your Source drive(s) [MKDIR for every Source directory specified in PATHS.CNF]! Utility UPDATE T can perform this step for you: respond "B"<cr> at the main UPDATE T screen to Make Backup Directories, then respond "M"<cr> to make Mirror-image backup directories -- but only AFTER you have fully Tested all path specifications. If, during execution, you are adding new backup directories to a pre-existing set, you will receive "Unable to create directory" messages: the indicated directories already exist. Note that you won't be permitted to Make Backup Directories until Target drive parameters are established in LASTDATE.CNF. If no LASTDATE file (page 22) UpDate User's Manual exists, UPDATE T creates LASTDATE.CNF before Making Backup Directories. (You can alter existing LASTDATE parameters in UPDATE T with the "C"hange LASTDATE command.) R = Root directory backups. Suppose that you wish to copy files from various discreet subdirectories on Source drives, to one large catch-all back- up "holding area" in Target drive Root directory(ies). In other words, you don't wish or care to have a Mirror-image of your Source directories on the Target(s). PROCEDURE: Respond `R' to set-up parameters c) and/or d), to make Root directory copying the default. If you have two identical hard drives, you have the IDEAL backup vehicle. 2) "Logical Drive" Systems [usually one actual hard drive] -----=======-=====----------------------------------------- If your system consists of various "logical" drives, i.e. one (or more) hard drive(s) subdivided into various "logical" drives or "partitions", each of which possesses a separate drive_letter designation, you may use one or two of your "logical" drives as back-up areas to collect all back-ups from the other "logical" drives. It is always a good idea, on a one hard-drive system, to make floppy back-ups also, for protection against a hard-disk crash. (See further the discussion of Parallel backup directories, #4 below). 3) Virtual [RAM] Disks. -------------===--===== UpDate is an ideal RAM disk back-up. Do your daily work on a RAM disk, for lightning speed. At the end of a session, before cutting power to the computer, run UpDate and store all new RAM files on your hard disk. Procedure: You need not (but could) put UpDate on your RAM disk. However, you require PATHS.CNF and LASTDATE.CNF files configured for use with the RAM disk. Suppose that D: is a RAM disk, and C: is a hard drive: PATHS.CNF might consist of the sole specification D:\ [Optional, additional LASTDATE.CNF Target 2 for floppy backup] Set LASTDATE.CNF Target 1 drive parameter a) to C Set LASTDATE.CNF Target 1 directory organization parameter c) to M or R In this example, run UpDate off C:, and it will transfer all new files from D: to C:. 4) Parallel hard-disk backup directories on single hard-drive systems. ----========-----------======-===========----------------------------- If you have ONE HARD-DISK ONLY, UpDate offers an optional enhancement to your directory organization: a duplication of files which is costly in (page 23) UpDate User's Manual disk space and may seem over-cautious, but which you will find both prudent and useful in any environment that drives its computer intensively. UpDate can create, for every master directory or subdirectory mentioned in PATHS.CNF, a "Parallel" hard-disk backup directory or subdirectory on the same hard-disk drive. This yields (among other advantages) an ultra-high-speed/hard-disk-only backup system, with a capability of subsequently backdating to the last floppy UpDate procedure and thus bringing your floppies "up-to-date" at any time. However, it cannot be used if you do not have plenty of available hard-disk space, equivalent at least to the combined size of all the files you will be backing up. Observe that Parallel back-ups are the FUNCTIONAL EQUIVALENT of Logical Drive UpDating on one real hard drive, with the same advantages and disadvantages. If a different "logical" drive is available for use, logical UpDating is more straightforward [DOS 3.1+ command SUBST makes different "logical" drives on a single hard drive]. The Parallel backup option allows you to recall older versions of files at any time, or consult a complete second fileset. It does NOT protect your data in case of total hard-disk failure, so back-up to floppies with prudent frequency. N.B.: Parallel backups may be made ONLY on Target 2! LASTDATE.CNF directory organization parameter d) is "P" (rather than "M" or "R"), and Target drive_letter parameter b) is BLANK (<cr>). Create Parallel hard-disk directories before first execution of UpDate, but AFTER your PATHS.CNF file has received the ** PATHS ARE OK! ** blessing from UPDATE T's path tester, and after LASTDATE.CNF is configured as per the preceding paragraph. Select the "B" (Make Backup Directories) option of UPDATE T, and create "P"arallel back-up directories on the same hard- drive(s) for specified source drive(s). It doesn't matter if some (or all) of these backup directories already exist (e.g. if you are adding new Parallel directories to a pre-existing set), because DOS will ignore a "Make Directory" instruction with the message "Unable to create directory" for those directories already in existence. Each independent Parallel back-up directory is nested at the same tree-level as the master (source) directory or subdirectory which it backs up. It bears a name identical to the name of the PATH from the ROOT directory to the SOURCE directory, plus the numeric suffix "1". Thus, for example, a C:\ART master directory has a Parallel back-up directory labelled C:\ART1. The only EXCEPTION to this "Suffix-1 rule" applies to a drive's Root directory which, because of DOS conventions, must be totally renamed: UpDate calls a Root directory Parallel backup area "drive_letter:\D", e.g. C:\D. A Parallel hard-disk backup directory need not contain programs or control files which never change (although it's often convenient to have a (page 24) UpDate User's Manual complete second system available anyway). If you have limited space on your one hard-disk, don't cram backup directories with "system files" because they never change. Bring floppies up-to-date at any time: PROCEDURE: The UPDATE.COM directory (or at least file LASTDATE.CNF) must be specified in PATHS.CNF. Each time you execute UpDate to floppy diskettes, a copy of the current Date/Time file (LASTDATE.CNF) should be written to one of those floppies. SUPPOSE that you decline to copy to floppies for one or more UpDate routines, and instead backup only to the "Parallel" hard disk directories (for hands-off convenience and high speed). Bring your floppies up-to- date by manually copying the latest LASTDATE.CNF file which resides on diskette to the UPDATE.COM hard-disk directory. Then run UpDate as usual, sending copies to the floppy Target. All files changed since the last FLOPPY UpDate procedure will be copied to floppies. 5) Dual-Drive or Single-Drive Floppy Diskette Systems (No Hard Drives!). -------------------------------======----------=======------------------ UpDate functions on computers with no hard drive. However, if the floppy drives are small-capacity (360K or less), UpDate system files will occupy approximately 60K bytes on EACH source diskette, and UpDate will require additional floppy (or RAM) disk space (typically to 50K) during operation. Therefore, UpDate is NOT RECOMMENDED for small-capacity floppy-only computer systems UNLESS run from a RAM disk. However, with high-capacity diskettes (e.g. 1.2M byte capacity), UpDate may perhaps be useful, because some users organize their diskettes to contain related groups of files, and they may fill a mere fraction of available space on these more spacious diskettes. Procedure: Suppose, as most IBM computers do, that A: is the PATHS.CNF Source drive. Whether you have one or two floppy drives, you must designate the Target drive as a DIFFERENT drive, e.g. B:, even if the ACTUAL destination drive is also A: (DOS resolves this problem internally): Set PATHS.CNF to read, e.g., A:\ Define LASTDATE.CNF Target 1 drive a) as B Define LASTDATE.CNF directory organization c) as R Run UpDate normally (page 25) UpDate User's Manual On ONE-DRIVE FLOPPY-ONLY systems, DOS will prompt you to swap source and destination diskettes as required; when DOS prompts to insert floppy B:, it really means that the destination diskette should be inserted in A: [prepare for a LOT of swapping!] On TWO-DRIVE FLOPPY-ONLY systems, designate the PATHS.CNF Source as "A:\" and LASTDATE.CNF Target 1 as "B". Run UpDate normally. A "Mirror-image" (sub)directory structure of floppy source disks can optionally be maintained on destination diskettes. Target 1-Only and Target 2-Only Path Specs. ========================================== N.B.: This section is relevant ONLY if UpDate addresses BOTH Target 1 AND Target 2 destinations. "Target 1-Only" and "Target 2-Only" specs may NOT be used if you send copies to one Target destination ONLY, and they are NOT a substitute for LASTDATE.CNF Target drive parameters! Definition: ---------- "Target 1-Only" and "Target 2-Only" specs are blanket path specifications for WHOLE directories, which restrict them to Target 1 ONLY [ &1] or Target 2 ONLY [ &2] copy destinations. Thus, these specs are used [VERY INFREQUENTLY] only if you USUALLY send directories/files to BOTH Target destinations, but wish to restrict copying of particular directories to a SINGLE Target. "Target 1-Only" and "Target 2-Only" specs are similar in format to "Skip filename" specifications [ &S], previously described, and PATHS.CNF is again the vehicle for these instructions. Suppose that one of your directories (e.g. C:\DATA) contains an important database; you maintain a complete, second backup fileset of this database on TWO Targets (e.g. hard and floppy). Suppose further that your OTHER directories and files don't require this degree of backup protection, or that you're pinched for hard-disk space; you want to back the others up to a single (floppy) target ONLY. You could accomplish this manually with Selective copy mode; but you can also pre-configure it with PATHS.CNF, so that it runs hands-off. This is possible with "Target 1- Only" and "Target 2-Only" specs. (page 26) UpDate User's Manual Example PATHS.CNF specifications (with gloss): line # ------ 1 C:\DATA (Normal spec: copy all \DATA files to either/both Targets) 2 C:\ART (Copy all directory \ART files ...) 3 C:\ART &1 (but copy them to Target 1 destinations only.) 4 C:\CHINESE\LETTERS &2 (Copy specified files from subdirectory \LETTERS to Target 2 destinations only, ...) 5 C:\CHINESE\LETTERS\TAN.TXT (for example, the letter to Tan ...) 6 C:\CHINESE\LETTERS\DENG.TXT &S (but skip Deng's letter.) Note some conceptual differences when " &1" and " &2" directory specs are used: "&1" and "&2" are akin to ENVIRONment statements about whole directories; you must ALSO specify the directories or individual filenames which you wish to monitor and copy, with REGULAR path specs. Thus, the sample directory specifications above indicate, in line 2, that ALL FILES in \ART will be copied (because the entire directory C:\ART is specified without filenames), but in line 3, that they will be copied only to Target 1 (no Target 2 back-up option will be offered). RULE: If you wish to back-up an ENTIRE DIRECTORY to one Target ONLY, make a general directory specification, and then REPEAT this specification with the appendage " &1" or " &2" (one blank space plus an ampersand "&" plus Target number "1" or "2"). The specs in lines 4-6 for subdirectory C:\CHINESE\LETTERS are different. Only individually specified filenames in \CHINESE\LETTERS will be copied, because there is no general specification for this (sub)directory. The "&2" spec in line 4 serves no function other than to inform the UpDate processor that individual filenames (e.g. line 5) will be copied to Target 2 backup areas only (no Target 1 option will be offered). RULE: If you wish to back-up SPECIFIC FILENAMES ONLY, specify the directory (without any filename) and append " &1" or " &2", then specify filename(s) individually. Wildcards are permitted in filename specifications. Locating and UpDating Newly-Added Files Bearing Old Dates. ========================================================= If you acquire a new program, and add its files to a directory specified in PATHS.CNF, the standard UpDate procedure will not copy them because they will usually bear creation-dates which PRECEDE the date/time recorded in LASTDATE.CNF. But UpDate's "Old CopyFile" option locates ALL files NEWLY-ADDED to PATHS.CNF directories which bear dates EARLIER than the date recorded in (page 27) UpDate User's Manual LASTDATE.CNF. It also flags differently-dated or -sized versions of filenames ALREADY located in your directories, e.g. if you acquire the latest implementation of a program. This "Old CopyFile" option is practical for modem users, who acquire date-stamped files (via the Ymodem protocol, or from ARChives and LiBRaries). The "Old CopyFile" option is enabled by entering "Y" in LASTDATE.CNF parameter "h". UpDate will deliver an integrated report with file copying of both OLD and NEW files. N.B.: The "Old CopyFile" option REQUIRES the presence of DOS file SORT.EXE in the UPDATE.COM directory. ======== The "Old CopyFile" option establishes (hands-off on the initial run), and thereafter maintains in the UPDATE.COM directory, an archival file called ARCH-UPD.CNF which serves as the reference for all old-date files. Each time you run the "Old CopyFile" option, current file listings are compared with ARCH-UPD.CNF, and all newly-added files dated EARLIER than the LASTDATE.CNF date/time record are flagged for copying. Upon normal completion of UpDate, a new ARCH-UPD.CNF is written to disk for reference on the next UpDate run. In the first ADVISORY listing of files, all "Old" files bear the appended tag "OLD". Old files may be SKIPped, or sent to Target 1-Only and Target 2-Only destination drives, just like standard UpDate. Because some additional processing time is required by "Old CopyFile" linkage, Old files can be collected in one directory only (e.g. a special modem download directory), with a separate "Old CopyFile" UpDate devoted to this directory. A standard UpDate system could then cover your other active directories for New files (but locate this UpDate system in a DIFFERENT directory!). The "Old CopyFile" option is established in LASTDATE.CNF set-up parameter h): respond "Y"es. If this parameter is changed to "Y" at runtime and the "Old CopyFile" option was not previously enabled, UpDate re-starts and creates a new archival file ARCH-UPD.CNF which will serve as the basis for comparison the NEXT time you run UpDate (no "Old CopyFiles" are copied on the first run). To disable the "Old CopyFile" option, respond "N"o to system parameter h). Although UpDate has just compiled a list of old files for copying, these will now be skipped, and only "new" files will be reported/copied. Differences Between Standard UPDATE and "Old CopyFile" UPDATE. ------------------------------------------------------------- Note that in standard UpDate, you can "backdate" the procedure and re- run it for identical results; but you can't normally REPEAT an "Old CopyFile" procedure with identical results: this option flags newly-added "old-date" files ONCE only (because the old ARCH-UPD.CNF file that spotted them is replaced by a new, current ARCH-UPD.CNF file). (page 28) UpDate User's Manual You can circumvent this restriction by copying an earlier ARCH-UPD.CNF file back into the UpDate directory. However, the older this file is, the more unpredictable the results. If you add new directories to PATHS.CNF between "Old CopyFile" runs, EVERY file in the new directories will be flagged. Deleting a PATHS.CNF directory has no effect. General Considerations. ====================== Remember that the UpDate procedure takes slightly more time as you add more directories or specific filenames (although not "Skip filename specifications" [ &S]) to PATHS.CNF. In an environment of intense use, backing up four or five directories once a day, you may complete UpDate in about 2-5 minutes if you manually switch floppies, and about 1-2 minutes if you back-up only to a hard disk in "Universal" copy mode. In both single-user and multi-user (multi-terminal) environments, you can install several UpDate modules in the system, e.g. one for your databases, another for your text files -- or one for each user -- but be sure to locate these modules in different directories! Password security should not present a problem, assuming that user possesses permission to enter each of the directories named in PATHS.CNF, and doesn't need to "show" his/her password every time these directories are accessed. Always enter path designations in PATHS.CNF for your master source directories only, and not for any backup directories. (page 29) UpDate User's Manual Summary of UpDate: First-Time Installation: Install UPDATE.COM in a directory Install LIST.COM/LIST.EXE in the same UpDate directory, to list files [optional] ["Old CopyFiles Option" only: Install SORT.EXE in the UpDate directory] List path specifications in the PATHS.CNF configure file Test PATHS.CNF to ensure that specified paths actually travel to their targeted directories or files, with the UPDATE T utility [Create back-up directories, if required, with the "B" ("Make Backup Directories") option of UPDATE T] Run UpDate and set-up LASTDATE.CNF Daily Operation: Set accurate current time & date in DOS on power-up [if necessary] Type UPDATE <cr> at DOS level, from the UpDate directory Reset time of last UpDate [optional] Choose Universal or Selective copying [optional] Indicate destination for back-up copies (Target 1, Target 2, or Both) Prepare to switch floppy diskettes [if necessary] (page 30) UpDate User's Manual Table of User Variables: Function Implementation -------- -------------- Current Date/Time DOS Alter LASTDATE.CNF Parameters/Backup Date and Time Runtime Directory to Copy [Path specification] PATHS.CNF Filename to Copy [Path specification] PATHS.CNF Directory to Copy to Target 1 Only [ &1 Path spec] PATHS.CNF Directory to Copy to Target 2 Only [ &2 Path spec] PATHS.CNF Filename to Skip (Omit-Copy) [ &S Path spec] PATHS.CNF Copy Old-Date Files LASTDATE.CNF Optional Copy/Skip Control [Selective mode only] Runtime/LASTDATE.CNF Copy Nonstop to Dir End [Selective mode only] Runtime Copy with Target Check [Selective mode only] Runtime Override Target Check [Selective mode only] Runtime Delete Source/Targets [Selective mode only] Runtime Abort to DOS [Selective mode only] Runtime Shell to DOS [Selective mode only] Runtime List/Type File [Selective mode only] Runtime Reverse Direction [Selective mode only] Runtime Run DOS Scripts [Selective mode only] Runtime View "List of CopyFiles" [Selective mode only] Runtime Target 1 and 2 UpDate All Files Runtime/LASTDATE.CNF Target 1-Only UpDate All Files Runtime/LASTDATE.CNF Target 2-Only UpDate All Files Runtime/LASTDATE.CNF _____________________________________________________________________________ Structure of sample LASTDATE.CNF files a = Target 1 Drive Designation b = Target 2 Drive Designation c = Target 1 Directory Organization d = Target 2 Directory Organization e = Target 1 Error Check f = Target 2 Error Check g = Universal/Selective Copy Mode h = Old CopyFiles option i = Delete .EXTensions (10) j = Scripts (9) Last Date Last Time (page 31) UpDate User's Manual UpDate Version History 1982 author's personal-use version 1.0 4 Apr 85 ArtTrack version 1.0 1.1 1 Jun 85 Configurable LASTDATE.CNF file Support for multiple hard drives and RAM disks 1.2 12 Aug 85 Extensive docs 1.3 15 Oct 85 Incorporated PATHS.CNF editor &Skip specs Nested conditional batch file logic 1.4 17 Oct 85 Simplified source 1.5 12 Nov 85 Parallel Suffix-1 directories 2.0 9 Jan 86 &Floppy/&Hard-only specs 2.1 22 Feb 86 New screens and docs 2.2 24 Apr 86 "Old CopyFiles" option 2.3 29 Apr 86 Revised docs and screens 2.4 9 May 86 Fixes to "Old CopyFiles" option 2.4x Fixes 2.5 22 May 86 Link/integrate "Old CopyFiles" with standard UPDATE New screens 3.0 3 Jun 86 New PATHS.CNF editor Enhanced error-checking 3.1 11 Jun 86 LIST/TYPE-file runtime facility 3.2 2 Aug 86 Space-checking on target drive 4.0 5 Sep 86 New, smaller UP.COM processor 5.0 22 Oct 86 Sweep-style UPDATE.COM (page 32) UpDate User's Manual Index Abort, runtime command to Quit..............................................19 Advantages of UpDate.........................................................2 Append specifications to PATHS.CNF..........................................10 Back-up directories, hands-off method for creating..........................24 Back-up drives, define......................................................13 Backwards processing: runtime "R"everse command.............................20 Buffers, number to install...................................................7 Change "last" backup Date and Time..........................................15 Check for existence of filename on Target 1/2...............................14 Clock limits, past and future................................................6 Copy mode, "Universal" or "Selective": default set in LASTDATE.CNF..........14 Copy to Root directories only...............................................23 Copy, runtime command.......................................................18 Cr, carriage return <cr> or "Enter" key......................................9 DATE and TIME functions (DOS), importance of.................................6 Date and time records of last UpDate procedure..............................12 Date/Time formats, must conform to USA (COUNTRY=001).........................6 Delete files, how to........................................................19 Delete specifications from PATHS.CNF........................................10 Destination directories, define.............................................13 Differences in operation between Standard UPDATE and "Old CopyFile" UPDATE..28 Directory paths, how to specify (UpDate).....................................8 Disk buffers, number to install..............................................7 DOS, runtime command to shell to DOS........................................19 Dual hard-drive copying.....................................................21 Duration of typical UpDate run..............................................29 Edit PATHS.CNF..............................................................10 Empty directory/filename specifications.....................................12 Enter key <cr>...............................................................9 Erase files, how to.........................................................19 EXTensions, automatic deletion or preservation by UpDate....................14 Floppy Backup Drive_letter, LASTDATE.CNF....................................13 Floppy-disk only directory specifications...................................26 Floppy-disk only, example specifications....................................27 Floppy-Only Systems: installation and use [and Limitations]...............25 Floppy-swapping, pause to enable in "Universal Copy Mode"....................6 Hard-Disk Backup Drive_letter, LASTDATE.CNF.................................13 Hard-disk only directory specifications.....................................26 Hard-disk only, example specifications......................................27 Hard-drive back-ups on single-drive systems (Parallel directories)..........23 LASTDATE.CNF set-up.........................................................12 LASTDATE.CNF, drive and directory designations, change......................16 Length of UpDate procedure, variables which affect..........................29 LIST file to screen during copy/skip/delete procedure.......................19 List of Files, first pass on-screen as an advisory..........................21 Logical drive copying: procedure...........................................23 Logical drives..............................................................22 (page 33) UpDate User's Manual Index Memory and disk space usage..................................................6 Menu, main, appearance of...................................................17 Mirror-image directories: definition.......................................22 Mirror-image, Parallel, or Root dir definition, LASTDATE.CNF................13 Multi-user considerations...................................................29 Newly-added files of older date, the "Old CopyFiles" option.................27 Nonstop processing, runtime command.........................................19 Old files, set LASTDATE.CNF default to copy.................................14 Parallel (Suffix-1) directories, definition.................................23 Parallel backup directories, on Target 2 ONLY...............................13 Parallel directories, installation (with UPDATE T's `B' option).............24 Parallel directories, theory and structure..................................24 Parallel hard-disk backup directories: Installation........................24 Password security, effect of................................................29 Path specifications, definition of...........................................7 Paths, examples of specifications............................................9 Paths, examples of specifications...........................................27 Paths, specifying for UpDate.................................................8 PATHS.CNF path specification file, definition................................8 PATHS.CNF, example specifications............................................9 PATHS.CNF, function .........................................................7 PATHS.CNF, how to specify directories/filenames..............................9 PATHS.CNF, philosophy.......................................................10 Purpose of UpDate............................................................2 Quick Start for Old Users....................................................3 Quick Start Instructions (for OLD USERS).....................................3 RAM disk copying: procedure................................................23 Re-organize PATHS.CNF with UPDATE T, necessity of...........................11 Reverse processing (go backwards)...........................................20 Scripts, DOS-level, runtime shell command...................................20 Scripts, DOS-level: execute during processing...............................14 Security, effect of.........................................................29 Selective copy mode: description...........................................17 Set-up.......................................................................7 Set-up of LASTDATE.CNF......................................................12 Shell to DOS during processing..............................................19 Single-drive hard-disk backup option (Parallel directories).................23 Skip filename specifications, definition.....................................8 Skip filenames, how to specify...............................................9 SORT.EXE required in UpDate directory for "Old CopyFiles" option............28 Specify filenames, or specify skip filenames: how to choose................10 Specify FILENAME[no .EXT] with wildcard ".*"................................12 Suffix-1 (Parallel) directories, definition.................................23 Test "Skip filename specifications" (not done)..............................11 Test PATHS.CNF, possible errors.............................................11 Test the validity of PATHS.CNF..............................................11 (page 34) UpDate User's Manual Index TIME function (DOS)..........................................................6 Two drives: copying between.................................................22 TYPE file to screen during copy/skip/delete procedure.......................19 Universal copy mode: description...........................................17 UpDate installation procedure................................................7 UpDate newly-added files of old date........................................27 UPDATE T, UpDate path specification test utility............................11 UPDATE T, UpDate's PATHS.CNF editor..........................................9 UpDate, everyday operation of...............................................12 UpDate, general description..................................................2 UpDate, quick operation checklist...........................................30 UpDate, repeating by backdating LASTDATE.CNF file...........................15 UpDate, run.................................................................12 UpDate, setting the date and time of last back-up procedure.................12 View the "List of CopyFiles"; runtime command...............................20 Virtual disk copying: procedure............................................23 Warning if wrong floppy diskette inserted in drive..........................21 (page 35)